Programmer/feeder system task linking program

ABSTRACT

A task linking program is provided for using a computer for interacting with on-line and off-line programming systems to perform tasks related to programming microdevices. The program is secure in being capable of being setup only in an administrator mode where microdevice, programming system, and other information can be inputted and changed. The program has an operator mode in which the program can only run the programming system. This provides the ability to employ relatively low skill operators to use the programming system.

CROSS REFERENCE TO RELATED APPLICATION(S)

The present application contains subject matter related to U.S. patentapplication Ser. No. 09/418,732, now U.S. Pat. No. 6,532,395 B1 by LevM. Bolotin entitled “MANUFACTURING SYSTEM WITH FEEDER/PROGRAMMING/BUFFERSYSTEM”. The related application is assigned to Data I/O Corporation andis hereby incorporated by reference.

The present application contains subject matter related to U.S. patentapplication Ser. No. 09/419,172, now U.S. Pat. No. 6,449,523 B1, byBradley Morris Johnson, Lev M. Bolotin, Simon B. Johnson, Carl W. Olson,Bryan D. Powell, and Janine Whan-Tong entitled“FEEDER/PROGRAMMING/BUFFER OPERATING SYSTEM”. The related application isassigned to Data I/O Corporation and is hereby incorporated byreference.

The present application also contains subject matter related to U.S.patent application Ser. No. 09/148,901, now U.S. Pat. No. 6,647,303 B1,by Simon B. Johnson, George Leland Anderson, Lev M. Bolotin, BradleyMorris Johnson, Mark Sean Knowles, Carl W. Olson, and Vincent Warholentitled “FEEDER/PROGRAMMING/BUFFER CONTROL SYSTEM AND CONTROL METHOD”.The related application is assigned to Data I/O Corporation and ishereby incorporated by reference.

TECHNICAL FIELD

The present invention relates generally to programming microdevices andmore particularly to remote task programming for programmer/feedersystems.

BACKGROUND ART

Originally, standalone desktop programmers were developed that took datafrom an operator, typically an engineer, and programmed it directly intoa programmable electronic microdevice. The mechanism for inserting andremoving the microdevice from the desktop programmer was an operator whomanually performed the task. The desktop programmer could only put datainto and take data out of a microdevice, and manipulate the data.

At the same time, there were companies that produced electronicmicrodevice labelers. These labelers contained a built-in printer andwould take labeling information, print a label, and place the label onthe microdevice. These systems were more automated. They could take anentire tube of microdevices and move the each microdevice though thesystem, labeling each microdevice and placing it back it an emptyreceiving tube. In this system, the operator only had to handle the tubeof microdevices and not each microdevice itself. However this systemcould only label parts.

A business, which needed to program and label microdevices, bought twocompletely different systems from two different companies. Then, as twoseparate processes they would program all their microdevices and thenlabel all their microdevices.

Subsequently, a system was created which merged the two systems. Theidea was to have an automated system that would program and label partstogether in one process. Not only did this reduce the number of steps inthe user's process, but it also eliminated the need for the operator tophysically touch the microdevice. Now the operator only needed to handlethe tubes of microdevices, inserting and removing them from the machine.The machine now did all the microdevice-by-microdevice handling,programming and labeling.

One big problem, however, was the two systems had no idea how to talk toeach other. They were not designed to work together or to know of theother's existence. One good point was each of the different systems hada remote control interface. Hence, a handling link program was createdthat used each systems' remote control interface to arbitrate processcontrol between the two systems.

With this arrangement, there existed a handling link program separatefrom a programmer program which was separate from a labeler program.They talked to each other, but generally were developed separately,updated separately, and in some cases developed by different companies.

During the development of the concept of a programmer/feeder system, itbecame apparent that a remote, non-connected control system and programwas desirable. Unfortunately, for many years the “legacy” systems, ortraditional systems, such as standalone programmers, had only focused onmicrodevice programming, data manipulation, and self-test capabilities.This meant that many new operations would have to be performed in a newprogram which can control both a programmer in an integrated system anda standalone programmer, where an operator has to manually insert themicrodevices.

The new program would have to use each systems' remote control interfaceto arbitrate process control between the systems. It would have toprovide a complete user interface for entering and storing allmicrodevice handling, labeling, and programming information. When anoperator selects the setup information it must be sent to each componentin the system. The new program would then have to start arbitrationwhile keeping each of the components working in synchronization duringthe process. It would have to keep track of statistic results for theoperations being performed. Ideally, the setup information would bestored to be easily used over and over again to run the samemicrodevices. Further, the new program would ideally also provide a modeof operation where an operator could manually, one by one, enter each ofthe parameters for programming a batch of microdevices and then justinitiate operation.

In addition, it was apparent that many businesses wanted to have thecapability of minimizing operator skill and dividing the operation ofthe new program into different parts than anything which had been donein the past. In essence, an engineering (free form) style user interfaceand a manufacturing (automated) style user interface were desired in oneproduct.

Thus, it was apparent that there would be many major problems indeveloping a programmer/feeder system program which could be controlledfrom a separate personal computer while still being able to controlpreviously developed legacy programming, labeling, and handling systems,and the systems which would evolve from them.

DISCLOSURE OF THE INVENTION

The present invention provides a task linking program for using acomputer for interacting with on-line and off-line processing systems toperform tasks related to processing microdevices. The program is securein being capable of being setup only in an administrator mode wheremicrodevice, processing system, and other information can be inputtedand changed. The program has an operator mode in which the program canonly run the processing system. This provides the ability to employrelatively low skill operators to use the processing system.

The present invention provides a task linking program for using acomputer for interacting with on-line and off-line programming systemsto perform tasks related to programming microdevices. The program issecure in being capable of being setup only in an administrator modewhere microdevice, programming system, and other information can beinputted and changed. The program has an operator mode in which theprogram can only run the programming system. This provides the abilityto employ relatively low skill operators to use the programming system.

The present invention provides a task linking program for using acomputer for interacting with a programming system to perform tasksrelated to programming microdevices. The program is capable of beingused with both directly connected traditional programming systems andindependent programming systems.

The above and additional advantages of the present invention will becomeapparent to those skilled in the art from a reading of the followingdetailed description when taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart of an administrator mode portion of the tasklinking program of the present invention;

FIG. 2 is a flow chart of an operator mode portion of the task linkingprogram of the present invention;

FIGS. 3A–3C is a flow chart of the programming of the present inventionfor legacy and related systems; and

FIGS. 4A–4B, is a flow chart of the programming of the present inventionfor a programmer/feeder system.

BEST MODE FOR CARRYING OUT THE INVENTION

The present invention relates to an overall system (not shown) whichconsists of three basic systems. First, is the computer system in whichthe program of the present invention operates. Second, is the legacyprocessing system, such as a programming system, which is on-line withthe computer. And third, is the new processing system, such as aprogrammer/feeder system, which is generally off-line or generallyoperates independently from the computer system.

Referring now to FIG. 1, therein is shown a portion of the task linkingprogram of the present invention to be referred to as the TaskLinkprogram for a wide variety of programming systems, some of them beingoff-line standalone programmers, some being desktop systems, and somebeing in-line systems, like a remote programmer/feeder system. In FIG. 1is shown a flow chart of an administrator mode portion 10 of theTaskLink program where an administrator, such as a manufacturingengineer or supervisor, creates and set up all the settings and savesthem.

The administrator starts the TaskLink program at a “Start TaskLink”block 12 with a display having a menu system and toolbars similar toMicrosoft Word or Excel. This type of display is used throughout theTaskLink program because of its familiarity to users. The program thenproceeds to “Change Systems Settings?” block 14 for the administrator toverify that the correct settings are in place for the systems theTaskLink program is set up to control. Mostly the system preferences aresettings that the administrator is expected to set when TaskLink isfirst installed, or expect to change very infrequently.

If there were a need to change the settings, there would be menus anddialog boxes in a “Change System Settings and Passwording” block 16 andbasically the administrator would pick from the menu system on thescreen to change the settings and indicate completion by clicking “OK”.

During the initial startup, the TaskLink program may be used to setup asecurity passwording system. This will prompt for a password which willbe preset to allow the program to operate subsequently in either anadministrator mode or an operator mode. The administrator mode allowsaccess to the entire program at an engineering level while the operatormode only permits processing microdevices with very limited presetselections. This provides a level of security which preventsunauthorized operators from making any changes in the program.

The new system settings would then get saved in a “Configuration File”block 18.

If there were no need to change the settings, the program would proceedto a “Start Task Manager” block 20. A “task” is defined as all theinformation necessary to process a component, such as a programmableelectronic microdevice (programmable electronic microdevices include,but are not limited to, electronically erasable read only memory(EEPROM), microcontrollers, and microprocessors), and a “kit” is definedas a series of tasks for example to process all the microdevices for asingle printed circuit board.

From the “Start Task Manager” block 20, the program proceeds to the“Create New Task?” block 22 from where the administrator would be ableto add a new one task with a new name at “Add New Task Name” block 24 orjust highlight an existing task at “Select Existing Task” block 26. Bothblocks proceed to an “Edit Task Parameters” block 28 where a task iscreated or edited. This is where settings are input or edited by aconventional editor, such as the name of the microdevice, theprogramming parameters, the data file parameters, etc. The editor iscapable of performing conventional editing functions as well asfunctions such as importing and exporting information from taskdatabases and ASCII task files.

After the task parameters have been edited in the “Edit Task Parameters”block 28, the program proceeds to a “Create/Edit Another Task” block 32to see if any other edits should be made. If there are further changesdesired, the program returns to a “Create New Task” block 22. If thereare not, the program goes to the “Exit Task Manager” block 34.

Referring now to FIG. 2, therein is shown a flow chart of an operatormode portion 40 of the TaskLink program where an operator merely usesthe program. The administrator mode portion in FIG. 1 describes thepreparation process for programming microdevices which would generallynot be run by an operator. The operator mode portion 40 is set up for alow-skill operator although an administrator may run this portion of theTaskLink program for quality assurance purposes.

As a result, after entry of the name and/or password in the “Enter Nameand/or Password” block 44, an authorized operator will proceed to a“Select Existing Task” block 50.

The “Select Existing Task” block 50 would have a list indicating thetasks, which the operator is allowed to perform, and permits theoperator to only select those tasks and set them to “run”.

The TaskLink program then proceeds to a “Program Microdevices” block 52.This block will be described in greater detail with reference to FIGS.3A–3C for on-line systems and FIGS. 4A–4B for off-line systems.

From the “Program Microdevices” block 52, the program proceeds to the“Run Another Task” block 54. Basically, the operator only has twochoices. Either another task can be run or the TaskLink program isexited.

Referring now to FIGS. 3A–3C, therein is shown the legacy and relatedsystem processing in the “Program Microdevices” block 52 in FIG. 2.Generally in these systems, the computer on which the TaskLink programresides is directly connected to the programming system by a local areanetwork, such as Ethernet.

Starting with FIG. 3A, after the “Select Existing Task” block 50 by theoperator, the TaskLink program checks in a “Multiple Microdevices?”block 62 to see if the names of multiple microdevices, multipleprocesses, multiple configurations within one task, and/or multiplesettings are within the existing task.

If the task contains multiple microdevices, processes, etc., the programgoes to a “Prompt for Microdevices” block 72 where the operator entersthe desired microdevices, processes, etc. to be run. This feature may beused, for example, where a business may be using two differentmicrodevices with one from a second source supplier. The purchasingdepartment may be changing microdevice suppliers on a weekly basis.Since it would be complex for the programming system to determine whichmicrodevice is currently being processed, it is easier preprogram theTaskLink program with the information for the different microdevices andto have the operator identify the particular microdevice to beprocessed.

If the task does not contain multiple microdevices and/or processes, theprogram proceeds to a “Send Setup Parameters to Programming System”block 74. The setup parameters are obtained by the “Send SetupParameters to Programming System” block 74 from the “Task File” block 30shown in FIG. 1.

After the “Send Setup Parameters to Programming System” block 74, theprogram proceeds to a “Transfer Data File to Programming System” block76 where the data files relating to the microdevices are transferred tothe programming system. For example, for a programmable microdevice, themicrodevice programming would be transferred at this point. Theintegrity of the data is then checked in a “Calculate and DisplayChecksum” block 78.

Next, the operator is prompted for the number of good microdevicesdesired out of the production run in a “Prompt for Pass Quantity” block80. This will let the processing run until the desired number orquantity of good or passable microdevices are programmed. Then, theprogram goes to a “Send Process-specific Setup to Programming System”block 82 to send out the appropriate setup information.

Since it is getting more common to provide serial numbers for processedmicrodevices, a “Serializing?” block 84 asks this question. If yes, aserial number is provided at an “Initial Serial Number” block 86. Theserial number is then transferred to the programming system by a“Transfer Serial Number to Programming System” block 88.

The program then returns to proceed in FIG. 3B.

In FIG. 3B, there are the visual directions, which are given to anoperator if manual feed of the microdevices is involved, or theprogramming where automated handling equipment is involved. In an“Insert Microdevice” block 90, the operator or handling equipment isinstructed to insert the microdevice into the programming equipment,such as a programmer.

Programming starts when the TaskLink program receives a signal in the“Microdevice Ready Signal” block 92. The TaskLink program then startsthe programming in “Start Programming” block 94. When the microdevice iscompletely processed, a return signal is received by the TaskLinkprogram indicating that the programming is complete and providingstatistical information in a “Programming Complete and Return Pass/Fail”block 96.

Upon completion of programming of the single microdevice, the TaskLinkprogram updates the displays and statistics in the “Update” block 98 andprovides an instruction in a “Remove Microdevice Signal” block 100. Theoperator or handling equipment then follows the instruction in a “RemoveMicrodevice” block 102. The TaskLink program then proceeds to FIG. 3C.

In FIG. 3C, the TaskLink program prepares for the next microdevice byagain asking about serialization in a “Serializing?” block 104. If yes,a serial number is provided at a “Create Next Serial Number” block 106.The serial number is then transferred to the programming system by a“Transfer Serial Number to Programming System” block 108. A check isthen made to determine if the appropriate number of good microdeviceshave been processed in a “Last Microdevice?” block 110. If no, theprogram returns to the “Insert Microdevice” block 90 where the operatoror handling equipment is instructed to insert the next microdevice intothe programming system. If yes, the TaskLink program starts shutdown ina “Send Any Necessary Shutdown Parameters” block 112.

The TaskLink program then goes to a “Final Display Update andStatistics” block 114 where final information is displayed and thenarchived in an “Archive Statistics and Serialization Data” block 116.This final information is then stored in a “Log File” block 118 and theTaskLink program finishes at a “Process Complete” block 120.

In the above, the computer and the TestLink program are in constantinteraction and contact and the contact may be described as being one ofan “on-line” connection between the computer system and the programmingsystem.

Referring now to FIGS. 4A–4B, therein is shown the programming for aprogramming system, such as a programmer/feeder system, in the “ProcessMicrodevices” block 52 in FIG. 2. Generally in these systems, thecomputer system on which the TaskLink program resides is not directlyconnected to control the programmer/feeder system and is connected toprovide and receive information periodically to and from theprogrammer/feeder system. However, it would be evident to those skilledin the art that nothing herein precludes a direct connection between thecomputer and the programmer/feeder system by a local area network, butthe operation would be one in which there would not constant interactionand contact. This type of contact where the computer is isolated fromthe programming system while the processing occurs is referred to as an“off-line” connection.

Starting with FIG. 4A, after the “Select Existing Task” block 50 in FIG.2 by the operator, the TaskLink program checks in a “MultipleMicrodevices?” block 150 to see if the names of multiple microdevices,multiple processes, multiple configurations, and/or multiple settingsare within the existing task.

If the task contains multiple microdevices, processes, etc., the programgoes to a “Prompt for Microdevices” block 152 where the operator entersthe desired microdevices, processes, etc. for programming.

Next, the operator is prompted for the number of good microdevicesdesired out of the production run in a “Prompt for Pass Quantity” block154.

Since the computer system is off-line while the programmer/feeder systemis processing in the preferred embodiment, the next step in “ValidateProgramming System Files” block 156 uses a portable memory medium in thecommunication process. The different types of portable memory mediainclude, but are not limited to, non-volatile electronic memory cards(such as PCMCIA memory cards), magnetic memory (such as mini-diskdrives), and optical memory (such as compact disk). In the preferredmode, a portable magnetic memory card is used.

The computer inserts information on to the portable memory card such asthat the proper programmer/feeder system is in place and to validatethat all the proper components for programming are in place on theprogrammer/feeder system.

If the computer system were connected to the programmer/feeder system bya local area network, the above operation would be performed directlyrather than by using a portable memory medium.

After validation, the TaskLink program will obtain information for thememory card in a “Get Setup Parameters and Format for System” block 158.The information is obtained from the “Task File” block 30 in FIG. 1 andthen formatted into a file that the programmer/feeder system expects toread. The information includes the microdevice being processed and itsoperational and programming characteristics. The format information isobtained from a Microsoft database file in “Microdevice InformationFile” block 162.

In a “Translate Data File” block 164, the programming data for themicrodevice from the “Program Data File” block 166 is decoded intobinary data.

In FIG. 4B, the binary data is checked in a “Calculate and DisplayChecksum” block 168 by checking sum and error correction bits.

The transfer of information for a complete job occurs at a “TransferComplete” block 170, where the information is loaded into the memorycard.

The next step is performed off-line from the computer and independent ofthe TaskLink program. This is indicated by a “Programming” block 172.This would be the programming or other processing information of thevarious microdevices. The off-line connection is denoted by a dot-dashline.

Upon completion of programming in the “Programming” block 172, the jobstatistics are returned at “Return” block 174 by the memory card. Theoff-line connection is again denoted by a dot-dash line. The TaskLinkprogram then goes to a “Final Display Update and Statistics” block 176where final information is received and then archived in an “ArchiveStatistics” block 178. This final information is then stored in a “LogFile” 180 and the TaskLink program finishes at a “Process Complete”block 182.

In summary, the operator in step one starts the TaskLink program on thecomputer and the program bundles up all the information, gathers all thesettings, etc., and writes a group of files out onto a memory card. Instep two, the operator takes that memory card over to theprogrammer/feeder system, plugs it in and then initiates the actual, thereal operation to run the programmer/feeder system. When theprogrammer/feeder system is finished it puts a statistics file back onthe memory card. Then, in step three, the operator takes the memory cardout of the programmer/feeder system and puts it in the computer so thatthe TaskLink program can archive the results and show the statistics inthe future.

From the above it will be understood that the present invention isapplicable to what can be described as “microdevices”. Microdevicesinclude a broad range of electronic and mechanical devices. The bestmode describes processing which is programming for programmable devices,which include but are not limited to devices such as Flash memories(Flash), electrically erasable programmable read only memories (E²PROM),programmable logic devices (PLDs), field programmable gate arrays(FPGAs), and microcontrollers. However, the present inventionencompasses processing for all electronic, mechanical, hybrid, and otherdevices which require testing, measurement of device characteristics,calibration, and other processing operations. For example, these typesof microdevices would include but not be limited to devices such asmicroprocessors, integrated circuits (ICs), application specificintegrated circuits (ASICs), micro mechanical machines,micro-electro-mechanical (MEMs) devices, micro modules, and fluidicsystems.

It will also be understood that the programmer/feeder system includesits own microprocessor for controlling its own operations. Thus, theportable media could also be used to update the software and thefirmware in the programmer/feeder system.

While the invention has been described in conjunction with a specificbest mode, it is to be understood that many alternatives, modifications,and variations will be apparent to those skilled in the art in light ofthe aforegoing description. Accordingly, it is intended to embrace allsuch alternatives, modifications, and variations which fall within thespirit and scope of the included claims. All matters set forth herein orshown in the accompanying drawings are to be interpreted in anillustrative and non-limiting sense.

1. A method for processing microdevices comprising: providing a computersystem having processing information related to microdevices as a task;providing a legacy processing system; providing a non-legacy processingsystem for operating independently from the computer system; providingthe task from the computer system to the legacy processing system withconstant interaction therebetween; providing the task from the computersystem to the non-legacy processing system for performing the task bythe non-legacy processing system independent of the computer system;developing return non-legacy information resulting from the non-legacyprocessing system using the task; returning the return non-legacyinformation to the computer system; providing the processing systemsetup parameters to the legacy processing system and the non-legacyprocessing system; providing the processing system shutdown parametersto the non-legacy processing system simultaneously with the processingsystem setup parameters; providing the number of processed microdevicesto be output from the legacy processing system and the non-legacyprocessing system; providing processing system process-specificparameters to the legacy processing system and the non-legacy processingsystem; controlling the handling of the microdevices; processing themicrodevices; providing the processing system shutdown parameters to thelegacy processing system; providing a number of microdevices;determining the number of microdevices processed; determining the numberof microdevices handled; and developing statistics from the number ofmicrodevices processed and handled.
 2. The method as claimed in claim 1additionally comprising: providing a microdevice programming system inthe legacy processing system, the legacy processing system having anon-line connection with said computer system; and programming themicrodevices in the microdevice programming system using the taskprovided through the on-line connection from the computer system to theprocessing system.
 3. The method as claimed in claim 1 additionallycomprising: providing an operator mode; providing a microdeviceprogramming system in the non-legacy processing system, the microdeviceprogramming system standing alone from the computer system; using theprocessing information for the task in the operator mode in thenon-legacy processing system independent from the computer system;returning return information in the operator mode from the non-legacyprocessing system using portable medium to the computer system; andstoring the return information in the computer system.
 4. The method asclaimed in claim 1 additionally comprising: providing an administratormode; providing programming information related to the task in theadministrator mode; editing the processing and programming informationrelated to the task in the administrator mode; and storing theprocessing and programming information related to the microdevices forthe legacy processing system and the non-legacy processing system as thetask in the administrator mode.
 5. The method as claimed in claim 1additionally comprising: serializing the microdevices; and maintaining alog of the serialized microdevices.
 6. The method as claimed in claim 1additionally comprising: combining a plurality of tasks to define a kit;and performing the processing of a kit in the legacy processing systemand the non-legacy processing system.
 7. The method as claimed in claim1 additionally comprising: providing microdevice information; providingprocessing system setup parameters; providing format information relatedto the non-legacy processing system; inputting the number of processedmicrodevices to be output from the non-legacy processing system;providing the processing system setup parameters and format to thenon-legacy processing system; transferring the microdevice informationfrom the computer system to the non-legacy processing system;transferring the processing system format from the computer system tothe non-legacy processing system; processing the microdevices; obtaininginformation from the processing of the microdevices; and transferringthe information from the processing of the microdevices to the computersystem.
 8. The method as claimed in claim 7 wherein the step of:transferring includes the use of a portable memory medium.
 9. The methodas claimed in claim 7 wherein the step of: transferring includes the useof a direct communication connection.
 10. The method as claimed in claim1 including the steps of providing an administrator mode; and protectingprovision of the operator mode using a password input in theadministrator mode.
 11. A method for processing and programmingprogrammable microdevices comprising: providing a computer system havingprocessing information and programming information related toprogrammable microdevices combined as a task in the computer system;providing a legacy processing system; providing a programmer/feedersystem for operating independently from the computer system; providingthe task from the computer system to the programmer/feeder system;performing the task by the programmer/feeder system independent of thecomputer system by processing and programming the programmablemicrodevices; developing return programmer/feeder information resultingfrom the programmer/feeder system using the processing information;returning the return programmer/feeder information to the computersystem; providing the processing system setup parameters to the legacyprocessing system and the programmer/feeder system; providing theprocessing system shutdown parameters to the programmer/feeder systemsimultaneously with the processing system parameters, providing thenumber of processed programmable microdevices to be output from legacyprocessing system and the programmer/feeder system; providing theprocessing system process-specific parameters to legacy processingsystem and the programmer/feeder system; controlling the handling of theprogrammable microdevices; programming the programmable microdevices;providing the processing system shutdown parameters to the legacyprocessing system; providing a number of programmable microdevices;determining the number of programmable microdevices processed;determining the number of programmable microdevices handled; anddeveloping statistics from the number of programmable microdevicesprocessed and handled.
 12. The method as claimed in claim 11additionally comprising: providing a microdevice programming system inthe programmer/feeder system, the programmer/feeder system having anon-line connection with said computer system; and performing the task bythe programmer/feeder dependent on the computer system using programminginformation obtained through the on-line connection.
 13. The method asclaimed in claim 11 additionally comprising: providing an operator mode;using portable memory medium to provide the task in the operator mode tothe programmer/feeder system independent from the computer system;returning return programmer/feeder information in the operator modeusing the portable memory medium to the computer system; and storing thereturn programmer/feeder information in the computer system.
 14. Themethod as claimed in claim 11 comprising: providing an administratormode; providing the processing and programming information related tothe task in the administrator mode; editing the processing andprogramming information related to the task in the administrator mode;and storing the processing and programming information related to theprogrammable microdevices for the legacy processing system and theprogrammer/feeder system in the administrator mode.
 15. The method asclaimed in claim 11 additionally comprising: serializing theprogrammable microdevices; and maintaining a log of the serializedprogrammable microdevices.
 16. The method as claimed in claim 11additionally comprising: combining a plurality of tasks to define a kit;and performing the programming of a kit in the legacy processing systemand the programmer/feeder.
 17. The method as claimed in claim 11additionally comprising: providing programmable microdevice information;providing programmer/feeder system setup parameters; providing formatinformation related to the programmer/feeder system; inputting thenumber of processed programmable microdevices to be output from theprogrammer/feeder system; providing the programmer/feeder system setupparameters and format to the programmer/feeder system; transferring theprogrammable microdevice information from the computer system to theprocessing system; transferring the programmer/feeder system form fromthe computer system to the programmer/feeder system; processing theprogrammable microdevices; obtaining information from the processing ofthe programmable microdevices; and transferring the information from theprogramming of the programmable microdevices.
 18. The method as claimedin claim 17 wherein the step of: transferring includes the use of aportable memory medium.
 19. The method as claimed in claim 18 whereinthe step of: transferring includes the use of a local area networkconnection.
 20. The method as claimed in claim 11 including the stepsof: providing an administrator mode; and protecting provision of theoperator mode using a password input in the administrator mode.
 21. Themethod as claimed in claim 11 including the step of: providinginformation for affecting changes selected from a group consisting ofsoftware, firmware, and a combination thereof by using a portable memorymedium.
 22. A method for processing microdevices comprising: providing acomputer system having processing information related to themicrodevices as a task; providing a legacy processing system; providinga non-legacy processing system; providing the task from the computersystem to the legacy processing system with constant interactiontherebetween; providing the task from the computer system to thenon-legacy processing system for performing the task by the non-legacyprocessing system independent of the computer system; developing returnnon-legacy information resulting from the non-legacy processing systemusing the task; returning the return non-legacy information to thecomputer system; providing a microdevice programming system in thelegacy processing system, the legacy processing system having an on-lineconnection with said computer system; and programming the microdevicesin the microdevice programming system using the task provided throughthe on-line connection from the computer system to the processingsystem.
 23. The method as claimed in claim 22 including additionallycomprising: providing the processing system setup parameters to thelegacy processing system and the non-legacy processing system; providingthe processing system shutdown parameters to the non-legacy processingsystem simultaneously with the processing system setup parameters;providing the number of processed microdevices to be output from thelegacy processing system and the non-legacy processing system; providingprocessing system process-specific parameters to the legacy processingsystem and the non-legacy processing system; controlling the handling ofthe microdevices; processing the microdevices; and providing theprocessing system shutdown parameters to the legacy processing system.24. The method as claimed in claim 23 additionally comprising: providinga number of microdevices; determining the number of microdevicesprocessed; determining the number of microdevices handled; anddeveloping statistics from the number of microdevices processed andhandled.
 25. The method as claimed in claim 23 additionally comprising:serializing the microdevices; and maintaining a log of the serializedmicrodevices.
 26. The method as claimed in claim 22 additionallycomprising: providing microdevice information; providing processingsystem setup parameters; providing format information related to theoff-line connection; inputting the number of processed microdevices tobe output from the processing system; providing the processing systemsetup parameters and format to the processing system; transferring themicrodevice information from the computer to the processing system;transferring the processing system format from the computer to theprocessing system; processing the microdevices; obtaining informationfrom the processing of the microdevices; and transferring theinformation from the processing of the microdevices.
 27. The method asclaimed in claim 26 wherein: transferring includes the use of a portablememory medium.
 28. The method as claimed in claim 26 wherein:transferring includes the use of a direct communication connection. 29.A method for processing and programming programmable microdevicescomprising: providing a computer system having processing informationand programming information related to the programmable microdevicescombined as a task in the computer system; providing a legacy processingsystem; providing a programmer/feeder system; providing the task fromthe computer system to the programmer/feeder system; performing the taskby the programmer/feeder system independent of the computer system byprocessing and programming the programmable microdevices; developingreturn programmer/feeder information resulting from theprogrammer/feeder system using the processing information; and returningthe return programmer/feeder information to the computer system;providing a microdevice programming system in the programmer/feedersystem, the programmer/feeder system having an on-line connection withsaid computer system; and performing the task by the programmer/feederdependent on the computer system using programming information obtainedthrough the on-line connection.
 30. The method as claimed in claim 29additionally comprising: providing the processing system setupparameters to the legacy processing system and the programmer/feedersystem; providing the processing system shutdown parameters to theprogrammer/feeder system simultaneously with the processing systemparameters; providing the number of processed programmable microdevicesto be output from legacy processing system and the programmer/feedersystem; providing the processing system process-specific parameters tolegacy processing system and the programmer/feeder system; controllingthe handling of the programmable microdevices; programming theprogrammable microdevices; and providing the processing system shutdownparameters to the legacy processing system.
 31. The method as claimed inclaim 30 additionally comprising: providing a number of programmablemicrodevices; determining the number of programmable microdevicesprocessed; determining the number of programmable microdevices handled;and developing statistics from the number of programmable microdevicesprocessed and handled.
 32. The method as claimed in claim 30additionally comprising: serializing the programmable microdevices; andmaintaining a log of the serialized programmable microdevices.
 33. Themethod as claimed in claim 29 additionally comprising: providingprogrammable microdevice information; providing programmer/feeder systemsetup parameters; providing format information related to theprogrammer/feeder system; inputting the number of processed programmablemicrodevices to be output from the programmer/feeder system; providingthe programmer/feeder system setup parameters and format to theprogrammer/feeder system; transferring the programmable microdeviceinformation from the computer system to the processing system;transferring the programmer/feeder system form from the computer systemto the programmer/feeder system; processing the programmablemicrodevices; obtaining information from the processing of theprogrammable microdevices; and transferring the information from theprogramming of the programmable microdevices.
 34. The method as claimedin claim 33 wherein: transferring includes the use of a portable memorymedium.
 35. The method as claimed in claim 34 wherein: transferringincludes the use of a local area network connection.